The committers listed above are authorized under a signed CLA.

• ✅ login: zakerf / name: zakerf (779c8af)

why is a fallback necessary?
as i do not see any breaking changes between 3.5.1 and 4.0.0
pivotal-cf/java-cfenv@v3.5.1...v4.0.0

@ramonskie I think calls to SpringBoot deps change when going from SpringBoot 3 -> 4, so you I guess you run into runtime "class not found" exceptions: e.g. pivotal-cf/java-cfenv@1dd9ccb

import org.springframework.boot.env.EnvironmentPostProcessor;
<-> 
import org.springframework.boot.EnvironmentPostProcessor;

@ramonskie the compatibility matrix also mentions that java-cfenv 4.x is for Spring Boot 4 and java-cfenv 3.x is for Spring Boot 3

cfenv should be added as a dependency-build and not be added within here in the manifest.
this way we will keep with updates
see https://github.com/cloudfoundry/buildpacks-ci/blob/master/pipelines/dependency-builds

we should add something like there in the config.yml

  cfenv:
    buildpacks:
      java:
        lines:
          - line: 3.X.X
          - line: 4.X.X
    source_type: github_releases
    source_params:
      - 'repo: /pivotal-cf/java-cfenv'
      - 'fetch_source: true'
    any_stack: true
    versions_to_keep: 1

im putting this here in the hope that ppl will understand the structure more clearly and that they could make a pr for this :)

cfenv should be added as a dependency-build and not be added within here in the manifest. this way we will keep with updates see https://github.com/cloudfoundry/buildpacks-ci/blob/master/pipelines/dependency-builds

we should add something like there in the config.yml

  cfenv:
    buildpacks:
      java:
        lines:
          - line: 3.X.X
          - line: 4.X.X
    source_type: github_releases
    source_params:
      - 'repo: /pivotal-cf/java-cfenv'
      - 'fetch_source: true'
    any_stack: true
    versions_to_keep: 1

im putting this here in the hope that ppl will understand the structure more clearly and that they could make a pr for this :)

Thanks! I'll prep a PR

the cfenv has now been added and updated see #1253 and #1251
so please adjust this pr
so we can merge it and include it within 5.0.2 release

the cfenv has now been added and updated see #1253 and #1251 so please adjust this pr so we can merge it and include it within 5.0.2 release

Rebased the branch to latest main to be up to date again

i do not like the hardcoded defaults. but for now it is okay is i do not expect it to change anytime soon

@ramonskie thanks for the support and merging the pr!